Skip to content
This repository was archived by the owner on Jul 11, 2023. It is now read-only.

release: Update versions to 0.9.0#3591

Closed
ksubrmnn wants to merge 1 commit intomainfrom
update_0.9.0
Closed

release: Update versions to 0.9.0#3591
ksubrmnn wants to merge 1 commit intomainfrom
update_0.9.0

Conversation

@ksubrmnn
Copy link
Contributor

@ksubrmnn ksubrmnn commented Jun 14, 2021

Signed-off-by: Kalya Subramanian kasubra@microsoft.com

Description:
Update osm version to 0.9.0

Affected area:

Functional Area
New Functionality [ ]
Documentation [X]
Install [ ]
CLI Tool [ ]
Certificate Management [ ]
Control Plane [ ]
Ingress [ ]
Egress [ ]
Networking [ ]
Observability [ ]
SMI Policy [ ]
Sidecar Injection [ ]
Security [ ]
Upgrade [ ]
Tests [ ]
CI System [ ]
Demo [ ]
Performance [ ]
Other [ ]

Please answer the following questions with yes/no.

  1. Does this change contain code from or inspired by another project?
    • Did you notify the maintainers and provide attribution?
      No
  2. Is this a breaking change?
    No

@ksubrmnn
release: Update versions to 0.9.0
d0414bf 
Signed-off-by: Kalya Subramanian <kasubra@microsoft.com>
@ksubrmnn ksubrmnn requested a review from a team as a code owner June 14, 2021 20:46
shashankram
shashankram suggested changes Jun 14, 2021
View reviewed changes
Copy link
Member

@shashankram shashankram left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR should be not created on the main repo branch.

@nojnhuh
Copy link
Contributor

nojnhuh commented Jun 14, 2021

@shashankram The release branch has already been updated (#3589), but yes, it would be good to hold off on merging this until the v0.9.0 docker images this references have been published.

@shashankram
Copy link
Member

shashankram commented Jun 14, 2021

@shashankram The release branch has already been updated (#3589), but yes, it would be good to hold off on merging this until the v0.9.0 docker images this references have been published.

I am suggesting to create a cherry-pick from release-v0.9 to main for this either directly using github or manually through a PR created from a fork.

@nojnhuh
Copy link
Contributor

nojnhuh commented Jun 14, 2021

Oh, I see what you mean now. I'm not sure it's worth recreating this PR from a branch of a fork. If the branch gets deleted right after this PR is merged, does it make a difference?

@ksubrmnn ksubrmnn closed this Jun 14, 2021
@ksubrmnn
Copy link
Contributor Author

ksubrmnn commented Jun 14, 2021

Closed in favor of #3592

@shashankram shashankram deleted the update_0.9.0 branch June 15, 2021 01:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

3 more reviewers

@shashankram shashankram shashankram requested changes

@allenlsy allenlsy allenlsy approved these changes

@nshankar13 nshankar13 nshankar13 approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@ksubrmnn @nojnhuh @shashankram @allenlsy @nshankar13